Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Cross-version deployment situations

You might well be maintaining an application running in both Dynamics release families at the same time. Two main categories of development might need to be deployed between these application versions:

New objects built in the development Repository.
Existing objects maintained in either Repository.

If you add new functionality to the application in one release family, you often add the same functionality to the application in the other family. If the implementation is identical in both families, it is simply a matter of developing it in one release Repository and exporting it to the other release Repository. Complications arise where you implement different application features or use different implementation techniques between the versions.

When you maintain existing objects between versions, aside from adding features to an object in one version that do not exist in another, you might use implementation techniques in one version that do not exist in another.

Any cross-version deployment must account for all of these scenarios.